Method for offering a protection policy for a mobile device

ABSTRACT

One embodiment includes a method for offering a protection policy for a mobile device, the method comprising the steps of providing an application, conducting a test of the mobile device, calculating the risk of protecting the mobile device, and offering an protection policy. The application is configured to operate on the mobile device and to test at least one function of the mobile device. The test is conducted by the application and verifies at least one function of the mobile device through the application. The risk of protecting the mobile device is based upon at least one result of the test. The protection policy for the mobile device is based upon the calculated risk, has a cost, and is offered for purchase to a user of the mobile device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S.application Ser. No. 14/157,462, filed on Jan. 16, 2014, which is acontinuation of U.S. application Ser. No. 13/152,141, filed on Jun. 2,2011 (now U.S. Pat. No. 8,635,092), which is a non-provisional of andclaims the benefit of U.S. Provisional Patent Application No. 61/350,837filed Jun. 2, 2010. The disclosures of the prior applications areconsidered part of and are incorporated by reference in the disclosureof this application.

TECHNICAL FIELD

This invention relates generally to the insurance field, and morespecifically to a new and useful method for offering an insurance policyfor a mobile device in the insurance field.

BACKGROUND

Mobile devices such as smart phones, tablet computers, electronic bookreaders, and other devices have seen an increase in usage in recentyears. Such devices in some cases have begun to displace the use of thedesktop computer. Mobile devices see much more frequent use throughoutthe day, which results in “wear and tear” damage to the mobile devices.Additionally, mobile devices are much more susceptible to being damaged,stolen, or lost. With so much value invested in mobile devices and withthe risk of losing or breaking the mobile devices being sufficientlyhigh, there are many benefits to having a protection policy, such as aninsurance policy, warranty plan, or some other suitable program, for themobile device. However, it is difficult for companies to assess the riskthey take on when protecting or insuring such devices. The state of themobile device when entering an insurance program is generally unknown.Even if visually inspected by an employee, there are numerous componentsthat are not easily tested. Many warranties and insurance options areonly available at the time of first sale because of the known state ofthe phone at that time. Thus, there is a need in the insurance field tocreate a new and useful method for offering an insurance policy for amobile device, wherein the insurance policy is based upon a calculatedrisk of insuring the mobile device and not necessarily based upon thedate of sale of the mobile device. This invention provides such a newand useful method.

Protection policies, such as warranties and insurance policies, formobile devices currently exist, but registration of a warranty orinsurance policy for a mobile device must be initiated within asubstantially short period of time following the sale of the mobiledevice. Furthermore, if a mobile device covered by a warranty orinsurance policy is damaged, the device must be taken to a customerservice center so the damage can be verified. This may present aninconvenience to the owner and/or user of the mobile device and may befurther disruptive to the owner and/or user if: the damage is shown tonot be covered under the warranty or insurance policy; the device isshown not to be damaged but instead inhibited by a configuration of themobile device (such as an “Airplane Mode” setting); or the owner and/oruser must wait in a line before a customer service representative willverify the damage of the mobile device. Thus there is a need in theinsurance field to create a new and useful method for verifying a claimon a protection policy for a mobile device. This invention also providessuch a new and useful method.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a flowchart representation of a method of a first preferredembodiment of the invention; and

FIG. 2 is a flowchart representation of a method of a second preferredembodiment of the invention.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

The following description of the preferred embodiments of the inventionis not intended to limit the invention to these preferred embodiments,but rather to enable any person skilled in the art to make and use thisinvention.

As shown in FIG. 1, a method of a first preferred embodiment foroffering a protection policy for a mobile device preferably includes:providing an application for testing the mobile device S105; testing amobile device S110; calculating device risk with results from the testS120; and offering a protection policy S130. The method functions toevaluate the operational state of the mobile device and facilitateenrollment in an appropriate program. The method is preferably for smartphones but may alternatively be for mobile phones, personal dataassistants (PDA), netbooks, tablet computers, electronic book readers,home entertainment devices, gaming devices, or any other suitablecomputing device. The method of the first preferred embodiment ispreferably designed for offering an insurance policy for a mobiledevice, but may alternatively be for a warranty, product registration,used-product pricing, and/or any suitable mobile device evaluation.

Step S105, which includes providing an application for testing a mobiledevice, functions to provide a platform upon which to test variousfunctions of the mobile device. Preferably, the application is madeavailable to the owner and/or user of the mobile device through theinternet or through an applications store. For example, the owner and/oruser may download the application from an iTunes Store or through an App(application) Store application already installed on the mobile device.Furthermore, the owner and/or user may download the application onto aseparate device and then transfer it to the mobile device, or theapplication may be installed on the mobile device before the mobiledevice is sold to the owner and/or user. Preferably, the application isa native application, but the application may alternatively be a webapplication or any suitable application configured to run on the mobiledevice. However, the application may be provided to the owner and/oruser and installed on the mobile device via any other method or methods.The application is preferably configured to operate on the mobile devicesuch that the application initiates the testing of at least one functionof the mobile device; the application may begin testing once accessed bythe mobile device, or the application may begin testing when prompted todo so by the user of the mobile device. The application may test one ormore functions directly, such as by sending a SMS message directlythrough the application to a remote server to test a cellular antennaarranged substantially within the mobile device. Alternatively, theapplication may command one or more external applications to test acertain function, such as by (1) prompting a Maps application operatingon the mobile device to determine the location of the mobile devicethrough GPS, and (2) prompting a Phone application operating on themobile device to determine the location of the device based upon therelation of the mobile device to three substantially proximal cellulartowers, and (3) comparing the locations determined by the Maps and Phoneapplications to ascertain a malfunction in the GPS or cellular antennasystems arranged substantially within the mobile device. The applicationmay initiate testing of one or more functions of the mobile device whilethe user of the mobile device is operating the application and theapplication is displayed on a screen of the mobile device;alternatively, the application may conduct testing discreetly while theuser of the mobile device is engaging other applications or functions ofthe mobile device or not using the mobile device at all. The applicationpreferably notifies the user of the mobile device that testing of themobile device is being conducted.

Step S110, which includes testing a mobile device, functions to collectdata that can be used to check the functionality of the mobile device.The testing of the mobile device preferably includes testingcommunication components S112, testing user interface components S114,testing device operational components S116, and/or testing any othersuitable components. The tests preferably target particular componentswith each test, though the tests may alternatively be combined to testmultiple components. The data collected from the tests is preferably abinary result representing if the component is “working” or “notworking”. The data may alternatively include more detailed data, such asdegradation of a function of the mobile device. In a first example, if ascreen is not fully functional, the results may indicate what portion ofthe screen is not functional. In a second example, a test may indicatethe capacity of a battery arranged within the mobile device as comparedto the capacity of that battery when new, such as by noting that theenergy capacity of the battery installed in the device has decreased bytwenty percent since new. The testing is preferably conductedimmediately preceding enrollment in an insurance program, but thetesting may alternatively have a waiting period. The testing mayadditionally include conducting extended background testing S118. Thebackground testing preferably functions to test components in a varietyof normal use situations, and may be used to classify the behavior ofthe user of the mobile device. For example, the application may trackinstances of large accelerations of the mobile device (or alternativelyaccess data that includes instances of large accelerations of the mobiledevice), wherein such large accelerations could indicate that the useris prone to dropping the mobile device and thus the risk of insuring themobile device for the user increases. Alternatively, the application maytake note of the amount of time that the phone is located within an areawith a known high rate of theft of mobile devices, which may increasethe risk of insuring the mobile device. Testing may include any suitablecombination of the described tests. The testing of a particularcomponent may be explicit, wherein the application provides instructionsand preferably guides the user through an interaction. The interactionsare preferably designed like a puzzle, game, test question or anysuitable format completed by the user. There may additionally be stepswherein the user lets the application complete background operations.The testing of any component may alternatively be a hidden test that isconducted without explicitly notifying the user that a particularcomponent is being tested. For example, when testing the ability to makea phone call, the microphone and speaker may additionally be tested forfunctionality.

Step S112, which includes testing communication components, functions toevaluate the ability of the mobile device to communicate throughavailable communication channels. The communication component testsduring Step S112 preferably tests a cellular antenna, a Wi-Fi internetconnection, GPS, Bluetooth, data link, and/or any other suitablecommunication components. Communication is preferably tested byestablishing a connection to another device using the communicationchannel, and then transferring a message. The message is preferablyautomatically transferred and confirmed. The message may alternativelyrequire user interaction to test the communication channel. Some of thetests may additionally require the user to complete tasks such as systemconfiguration. For example, the user may be required to access a Wi-Finetwork, turn off Wi-Fi, turn on Bluetooth, etc. Such systemconfiguration tasks may be performed outside of the test app. In onevariation, the Wi-Fi and/or cellular antenna may be tested byestablishing a HTTP connection to a test server (any suitable internetprotocol may be used), and the test server preferably transmits aspecified message. The application on the mobile device preferablyverifies that the expected message is received. The application mayadditionally send a message to the test server over the internetconnection. As another variation, the cellular antenna may be tested byinitiating a phone call to the phone number of the mobile device. Anautomated voice system preferably reads a message to the user, whoinputs the message into a text field of the app. The user mayadditionally be required to repeat set phrases to the automated voiceapp, and user commands are then preferably confirmed. This variation hasthe additional benefit of combining testing of communication componentswith testing user interface components (i.e., speaker, microphone andproximity sensor). For location devices, the user may be required toenter their current address and that location information is compared tolocation information received by the GPS component. Cellulartriangulation information may additionally be used to test the GPSand/or cellular antenna. In another variation, Bluetooth or othershort-range communication protocols may be tested by connecting to asecond device. A test program on a desktop computer or other computingdevice preferably sends and receives test communication messages. Thedata link port (e.g., a USB connection port) may additionally require auser to connect the mobile device to a computer running a test program.The test program then preferably verifies that communication can beachieved through the data link cable/connection.

Step S114, which includes testing user interface components, functionsto evaluate the functionality of user input and feedback devices of themobile device. The user interface component tests during Step S114preferably tests a screen, speaker, headphones, microphone, camera,accelerometer, gyroscopes, compass, touch screen, buttons, hapticfeedback devices, proximity sensors, or any suitable user interfacecomponent. The tests preferably target each user interface component.Many of the tests require a user to complete a task and if the task isnot correctly completed, the tested component may be identified as beingnon-functional. The tests may have any suitable level of redundancy.

A screen is preferably tested by displaying various graphics on thescreen. In one example, a series of tests displays information indifferent locations of the screen and requires the user to enter thedisplayed information. The touch screen may similarly be tested byrequiring the user to trace a finger along a specified path whereby thetouch sensing capabilities of the mobile device may be detected.Alternatively, while proceeding through the application, virtual buttonsor user interface elements of the application may be positioned invarious locations. In this variation, the touch screen and possibly thescreen may be tested without alerting the user to the testing of thetouch screen or screen.

Buttons, scroll balls, and any suitable analog input devices arepreferably tested by requiring user activation of the inputs. Forexample, a QWERTY keyboard is preferably tested by requiring a user totype a pangram such as “The quick brown fox jumps over the lazy dog”.Other buttons such as arrow, menu, volume, and/or other buttons mayadditionally require a user input to test. If a button cannot betriggered by the user, then the button is preferably identified asbroken or non-functioning.

A speaker and/or headphone jack is preferably tested by playing arecording. The user preferably is required to identify the contents ofthe recording, such as a message or timing of sounds. A microphone ispreferably tested by recording a set phrase spoken by the user. As anadditional alternative, the speaker and microphone may perform acoordinated test, where the microphone records the sounds produced bythe speaker. This alternative preferably removes the possibility ofhuman error and allows more sophisticated audio tests to be performedsuch as testing the range of the speaker and microphone. The speaker andmicrophone preferably have a known sound response profile that can beused as reference for evaluating the test results.

A camera is preferably tested by taking a photo. The photo may be of anysuitable object, but the photo may be of a standard object such as animage printed for the test or any suitable object.

An accelerometer, gyroscope, compass, and/or any suitablemotion/orientation sensor is preferably tested by instructing the userto move the mobile device in particular ways such as shaking, tiltingup, rotating, or any suitable motion. The sensor range and sensitivityis preferably evaluated by recording the sensor signals during themotions. One exemplary test of the compass is preferably conducted byinstructing the user to rotate in a full circle while holding the mobiledevice outward. In this exemplary test, the compass sensor wouldpreferably produce a sensor signal for substantially the whole range ofcardinal directions.

Haptic feedback devices preferably include vibrational motors,piezoelectric vibrators and any suitable physical feedback device. Ahaptic feedback device is preferably tested by having a user providefeedback when the haptic feedback device is activated. For example, theuser may be required to tap a button in response to a vibration. Thehaptic feedback device may alternatively be pulsed in a pattern thatpreferably tests different levels of activation. As an alternative, thehaptic feedback device and a motion sensor such as an accelerometer orgyroscope preferably perform a cooperative test. The haptic feedbackpreferably generates expected levels of motion that are preferablydetected by an accelerometer, gyroscope or any suitable motion sensorarranged substantially within the mobile device. This variationfunctions to automate the process of testing the haptic feedback deviceand motion sensor.

A proximity sensor, as is sometimes used to detect when a phone is heldup next to the ear of a user, is preferably tested by instructing theuser to hold the phone up to his or her ear. The proximity sensor mayalternatively be tested in the background when the ability to make aphone call is tested (assuming the user places the phone to his or herear during the call).

Step S116, which includes testing device operational components,functions to evaluate the functionality of basic hardware and softwarecomponents of the mobile device. The component tests of Step S116preferably test the operating system, battery, hard drive or memory,memory card reader, SIM card reader, processor, and/or any other systemarranged on or within the mobile device. Step S116 may include checkingmodel numbers or version numbers. The model number or version number ofthe mobile device can preferably be used to detect if the mobile deviceincorporates any replacement parts and/or modifications. Model numbersor version checks may additionally be used to determine the age of thephone. For example, tests for the operating system may detect if thephone has been “jailbroken” (i.e., manufacturer restrictions removed),if the SIM card has been unlocked (i.e., modified to accept any SIM), orif any suitable non-standard modification has been performed. Othercomponents are preferably tested by performing basic operations such asreading and writing data to memory to test the hard drive/memory of themobile device. Step S116 preferably includes recording battery health(capacity), number of charge cycles, and any other suitable information.The device component tests are preferably background tests, and occurautomatically. In some cases, Step S116 may additionally includedetecting the applications installed on the mobile device, theidentification number of the mobile device, the version of the operatingsystem operating on the mobile device, most recent use data of themobile device, the date of first use of the mobile device, the cellularprovider, the cellular plan usage, or any other information. Thisinformation can preferably be used when calculating the risk of insuringthe mobile device. The information may alternatively be used to create auser profile. The user profile is preferably used to classify the typeof user of the mobile device, such as if the user employs the mobiledevice for business, games, media, family, etc.

Step S118, which includes conducting extended background-testing,functions to perform tests over a long duration. The steps of S112,S114, and S116 may be performed in a single short session with theapplication (e.g., around one minute). Step S118 functions to performlonger duration tests. The application preferably operates in thebackground for an extended period of time such as a day or a week, whichfunctions to collect data from the phone during normal operation.Various sensors preferably collect periodic data. For example GPS andaccelerometer data is preferably collected. The data may be used toclassify the user into particular behavioral pools. For example, thefrequency of use of the phone may be detected based on movement, phonenetwork usage, network usage, etc. As another example, from location andmotion data, analysis could preferably indicate if the user uses themobile device while running, travelling, or performing other suitableactivities.

Step S120, which includes calculating risk of insuring the mobile devicewith results from the test, functions to determine an appropriateinsurance policy or program enrollment rate. The operational state ofthe various components is preferably collectively considered whencalculating risk. If all components pass, the risk is preferably low. Ifa component of the mobile device experienced a failure or hadquestionable/non-standard performance, then the risk is preferablyhigher. If most or all components failed, then the risk is preferablyvery high, possibly to the extent that the mobile device is no longerinsurable. In one embodiment, the risk preferably determines the resellvalue of the mobile device, wherein the resale value is based upon thefunctionality of the mobile device and the degradation of function ascompared to the mobile device when new. Calculating risk mayadditionally include factors like age of the mobile device, which may bedetermined in Step S116 or in any suitable fashion. Calculating risk mayadditionally include factoring in user profiles created during thetesting. In another embodiment, the risk calculation preferably verifiesthat all required components and factors match a desired state. If theall the information passes, then the mobile device is preferablyeligible for an insurance policy. The calculation of the risk ofinsuring the mobile device may be performed from within the application;in this example, the application incorporates a set of rules, aguideline, an algorithm, etc., to calculate risk based upon thefunctionality of the mobile device as determined by the application.Alternatively, the calculation of risk of insuring the mobile device maybe performed substantially remote from the mobile device. For example,the application may transmit data pertaining to the functionality of themobile device to a server arranged substantially remote from the mobiledevice, wherein risk is calculated on the server (or in the “cloud”).Data may be transmitted to the server piecemeal, such as after each testor series of tests, or as one lump data packet containing results of alltests performed. The application may then receive information regardingthe risk of insuring the mobile device and thus determine an appropriateinsurance policy based upon this information; alternatively, theapplication may simply receive information regarding an appropriateinsurance policy based on the risk as determined substantially remotefrom the mobile device.

Step S130, which includes offering a protection policy, functions tocomplete the enrollment of the mobile device. Preferably, Step 130includes offering an insurance policy for the mobile device. Aprotection policy corresponding to the device risk calculated in StepS120 is preferably presented and described within the app, and the usermay complete the enrollment in and/or purchase of the protection policyfrom within the application. In this embodiment, the user preferablysubmits payment information (such as checking account direct billinginformation or credit card information) through the application, whereinthe application transmits the payment information to a server arrangedsubstantially remote from the mobile device and configured to manageprotection policy accounts. The application preferably encryptsinformation, specifically payment information, to encryption standardssuch as the Data Encryption Standard (DES), Triple Data EncryptionStandard (3-DES), or Advanced Encryption Standard (AES); the applicationmay also use cryptographic protocols such as Diffie-Hellman keyexchange, Wireless Transport Layer Security (WTLS), or any othersuitable type of protocol to protect user information. In the embodimentin which test results are transmitted to a remote server, this data mayalso be encrypted. However, the application may also direct the user toa second application operating on the mobile device or a website inwhich the user may enroll in and submit payment for the protectionpolicy. Alternatively, a reference number is preferably provided to theuser (such as from within the application or emailed to an email addressprovided by the user when the application was installed on the mobiledevice), and the user may use this reference number later to completethe enrollment in and/or payment for the protection policy. Step S130 ispreferably used to provide an insurance policy for the mobile device,but may alternatively be for a warranty, product registration, and/orany suitable mobile device enrollment. As an additional alternative,used-product pricing or other suitable mobile device evaluation may beoffered.

The above method is preferably implemented in a computer-readable mediumstoring computer-readable instructions. The instructions are preferablyexecuted by computer-executable components of a mobile device and othersupporting devices such as a test server. The computer-readable mediummay be stored on any suitable computer readable media such as RAMs,ROMs, flash memory, EEPROMs, optical devices (CD or DVD), hard drives,floppy drives, or any suitable device. The computer-executable componentis preferably a processor but the instructions may alternatively oradditionally be executed by any suitable dedicated hardware device.

As shown in FIG. 2, a method of a second preferred embodiment forverifying a claim on a protection policy for a mobile device preferablyincludes: providing an application for testing the mobile device S205;receiving a claim on a protection policy 208; testing a mobile deviceS110; comparing the claim to the results of the test; and accepting orrejecting the claim. The protection policy is preferably an insurancepolicy and provided to the user and/or owner of the mobile device asdescribed above, but protection policy may be of any other type andproduced by any other suitable method. The method of the secondpreferred embodiment functions to evaluate the operational state of themobile device, compare it to a previous or expected state, and accept orreject a claim for damage to (or problem with) the mobile device. Themethod is preferably for smart phones but may alternatively be formobile phones, personal data assistants (PDA), netbooks, tabletcomputers, electronic book readers, home entertainment devices, gamingdevices, or any other suitable computing device. The method ispreferably designed for evaluating a claim on an insurance policy for amobile device, but may alternatively be for evaluating a claim on awarranty or any other suitable mobile device protection programevaluation.

Step S205, which includes providing an application for testing a mobiledevice, functions to provide a platform upon which to test at least onefunction of the mobile device. Preferably Step S205 is substantiallysimilar to Step S105 of the first preferred embodiment, wherein theapplication of Step S205 is loaded onto the mobile device in a methodsimilar to that of the application of Step S105. The applicationdescribed in Step S205 may be the same application as that described inStep S105. Alternatively, the user of the mobile device may download theapplication of Step S205 only after downloading the application of StepS105 and enrolling in the insurance policy described in Step S130.Preferably, the user of the mobile device is enrolled in a protectionpolicy for the mobile device before accessing the application of StepS205.

Step S208, which includes receiving a claim on the insurance policy forthe mobile device, functions to identify potential damage to or apotential problem with the mobile device. Preferably, upon discovery ofa potential issue with the mobile device, the owner and/or user of themobile device submits the claim to the protection (i.e. insurance orwarranty) company for processing. Preferably, the user accesses theapplication of Step S205 and selects a problem with the mobile devicefrom a list of potential problems from within the application.Alternatively, the user may contact a customer service representative ofthe company providing the protection policy for the mobile phone anddescribe the problem; the user may also access a website and submit theclaim to the insurance company therein; or the user may advise thecompany of the problem by any other method. If the claim is advisedsubstantially remote from the mobile device, such as not from within theapplication of S205 installed on the mobile device, then a report of thepotential problem is preferably transmitted to the application.

Step S210, which includes testing a mobile device, functions to collectdata that can be used to check the functionality of the mobile device.Preferably, Step S210 of the second preferred embodiment functionssubstantially similar to Step S110 of the first preferred embodiment. Asin S110, a plurality of functions of the mobile device may be tested inS210. If all functions or all primary functions (such as the ability tomake and receive phone calls and to send and receive SMS messages) ofthe mobile device are tested in S210, the application may determine anproblem(s) with the mobile device in addition to the problem related tothe claim as indicated by the user of the mobile device; the applicationmay inform the user of the additional problem(s). Alternatively, onlyone or only a subset of functions described in the claim may be testedin S210, which may reduce the amount of time required to test the mobiledevice and to verify the claim. If the application determines that theproblem related to the claim (or an additional problem discovered by theapplication) is fixable by the user, the application preferably suggestsa method by which the user may solve the problem. For example, if theuser determines that the mobile device will not accept pushnotifications and reports this to the application as a problem ordefect, and the application determines there is no defect with themobile device but rather the settings of the mobile device are notsuited to a need or desire of the user, the application may suggest thatthe user change the notification settings of the device to alleviate theproblem.

Step S220, which includes comparing the claim to the results of thetest, functions to verify the claim. The application collects dataregarding the state of the mobile device, specifically the functionalityof the mobile device, in order to identify faulty or fraudulent claims.Preferably, the application performs the comparison while operating onthe mobile device. In this example, the application may store dataregarding the results of the tests locally on the mobile device and thendetermine the merit of the claim based upon this data. Alternatively,the application may transmit data pertaining to the functionality of themobile device to a server arranged substantially remote from the mobiledevice, wherein the comparison of the claim and the state of the mobiledevice is performed on the server. Data may be transmitted to the serverpiecemeal, such as after each test or series of tests, or as one lumpdata packet containing results of several or all tests performed.

Steps S230 and S240, which includes accepting or rejecting the claim,function to inform the owner and/or user of the mobile device of thestatus of the claim. Preferably, the application performs the comparisonof the claim to the functionality of the mobile device and provides theresult of the comparison to the user through the application within asubstantially short period of time after the claim was first received bythe application (such as within one minute). In this variation, theapplication may inform the user that the claim was accepted (when theclaim matches the functionality of the mobile device as tested) andallow the user to select a method of repairing or replacing the mobiledevice. The application may also inform the user that the claim wasrejected (such as when the claim does not match the functionality of themobile device as tested or the defect is not covered by the insurancepolicy). Alternatively, the application may provide a reference numberto the user, wherein the user may later use the reference number tocheck the status of the claim, such as on the internet in a web browseror over the phone with a representative of the company providing theinsurance policy. However, the status of the claim may be determined andpresented by any other method or methods.

As a person skilled in the art will recognize from the previous detaileddescription and from the figures and claims, modifications and changescan be made to the preferred embodiments of the invention withoutdeparting from the scope of this invention defined in the followingclaims.

1-4. (canceled)
 5. A method for offering protection services for amobile device, the method comprising the steps of: providing anapplication to test at least one function of the mobile device, whereinthe testing includes background testing to determine a typicaloperational use of the mobile device and functional testing to test oneor more functional aspects of the mobile device; conducting a test of atleast one function of the mobile device through the application or ananalysis of data collected from the device by the application todetermine typical operational use or condition of the mobile device;calculating, by a computer, a risk associated with providing one or moreoffers for protecting the mobile device based upon at least one resultof each test; and presenting, to a user of the mobile device, an offerrelating to the mobile device, wherein the offer is based upon thecalculated risk and has a cost.
 6. The method of claim 5, wherein theoffer comprises an offer for a protection policy.
 7. The method of claim5, wherein the offer comprises an offer to replace the mobile device. 8.The method of claim 5, wherein the offer comprises an offer to repairthe mobile device.
 9. The method of claim 5, further comprisingreceiving a request for the offer related to the mobile device.
 10. Themethod of claim 9, further comprising accepting the request for theoffer related to the mobile device based on the risk.
 11. The method ofclaim 9, further comprising notifying the user of the mobile device of astatus of the request through the application.
 12. The method of claim5, wherein the testing comprises testing at least one of an antenna, atransmitter, a display, a GPS system, a battery, or memory of the mobiledevice.
 13. The method of claim 5, wherein the mobile device is selectedfrom the group comprising a smart phone, a mobile phone, a PDA, anetbook, a tablet computer, an electronic book reader, a homeentertainment device, and a gaming device.